Welcome, Guest: Register On Nairaland / LOGIN! / Trending / Recent / New
Stats: 3,151,054 members, 7,810,939 topics. Date: Saturday, 27 April 2024 at 06:52 PM

:: Dhtml Framework Evolution - Webmasters (2) - Nairaland

Nairaland Forum / Science/Technology / Webmasters / :: Dhtml Framework Evolution (5971 Views)

DHTML, Or Perhaps Other Developers, I Need You. / Flex Builder Tutorial / Using Some Dhtml Techniques / My Dhtml Board Games Project :: Featuring Ludo, Snakes And Ladder (2) (3) (4)

(1) (2) (3) (Reply) (Go Down)

Re: :: Dhtml Framework Evolution by Nobody: 1:40pm On Jul 02, 2009
Highlight:
This framework like i said is going to be both client/server-sided. The current version i am using for my projects
are all written by me - i wrote most of them at the begining of my learning to develop myself. . .

I observed that most of the client-sided areas are somewhat similar to jquery - www.jquery.com while most of the server side
are similar to php::pear - http://pear.php.net/

Both of them are open-source. Now, using those libraries will help faster to make things easier to follow. Any knowlege you
have on those libraries will be appreciated, and if you do not know how to use the libraries, you will still be able to use the
framework, but to a limited extent. I am using those resources to make the work easier for me, and not to re-invent the wheel.

I can write jquery modules/plugins, and i can create pear classes too. . . i will use that knowlege to tie things together here.
I am not going to start a thread on any of those 2 platforms, they are well documented on their respective websites already.

Updates will come later. Meanwhile, i am thinking of doing some stuffs for SMFs later, and i have not forgotten my ludo game. . .
Re: :: Dhtml Framework Evolution by Nobody: 6:48pm On Jul 08, 2009
For simplicity sake, i have decided to merge my modules with pear and jquery. . . .those ones are well documented stuffs
So rather than releasing the library as it is, i will convert them into jquery plugins and pear modules.
Then i will implement them here, and also get to do my ludo and some other stuffs.

By the way, i develop stuffs with firefox, and i make good use of firebug and firephp, and i will support them in future releases.
I will keep you guys posted on happenings. Meanwhile, i hope i am safe to assume that most developers have pear installed
on their development/deployment server?
Re: :: Dhtml Framework Evolution by quadrillio(m): 3:51pm On Jul 09, 2009
Patiently waiting,
Re: :: Dhtml Framework Evolution by cdeveloper(m): 12:40am On Jul 14, 2009
It is been a while i saw the post on Framework here and Framework there but i am yet to see a url either on Google Open source project hosting or sourceForge code hosting for the work to be reviewed if not by the veteran programmers at large, at least by fellow programmers in Nigeria. However, one thing i look out for in a Framework is the extensibility of such Framework through plugins. Its am open source Framework i suppose meaning it is not written in an abstract language. Best of luck man.
Re: :: Dhtml Framework Evolution by Nobody: 6:01am On Jul 14, 2009
@cdeveloper, you are very right there. I have the stuff ready, i want to make sure it is standardized.
That is why i am researching properly, and want to build it on existing frameworks like jquery. There
are several parts similar to jquery. I am going to support jquery all the way, right now i am mastering
the jquery UI development (that is my last area to master in jquery), i am ok with pear. I am not in a
rush to release rubbish.
Thanks for the advice.
Re: :: Dhtml Framework Evolution by Nobody: 9:36am On Jul 24, 2009
Once again, i was overtaken by client work. Meanwhile i have started revamping my website: www.mwebng.net
For now, i only altered the background a little to be sharper, and also optimized the javascript/css to load about
2 - 4 times faster than before (a rough estimate though).

I am still going to work on the contents later. I mentioned my site revamping because it lead me to another idea.
My site runs on its own little library (made specially for it) with the javascript made up of about 5 files (total of 45KB)
compressed to 23KB. Now that is a reasonable size to me, and i will leave it that way for now. And work more on the contents.

I intend to integrate jquery later for the upgrade version, which i have started already. I am not making changes to the layout
but rather to make the content dynamic, and more useful to myself and others.


So, what i have in mind is to just release the interesting codes in bits and pieces (well documented) and allow people to make
up their minds on what they wish to do with it. Plus of course room for modifications.
Re: :: Dhtml Framework Evolution by Nobody: 6:01am On Jul 25, 2009
A little Quiz Teaser:

Here is a little scenario, you want to increase the loading speed of this site,
The site has 5 files as shown below:
(Lemme see some attempts on this before i release part of my lib code)

/home.html
/style/default.css
/style/home.css
/js/default.js
/js/home.js
Re: :: Dhtml Framework Evolution by Nobody: 6:04pm On Jul 25, 2009
No reply still? must mean, it is either too simple, or too hard
Re: :: Dhtml Framework Evolution by Nobody: 9:36pm On Aug 01, 2009
Just added it to google http://code.google.com/p/dhtmlframework/
I am still working on the javascript frontend. I had to build a javascript framework, more like
studied and borrowed some parts of jquery, so many of the syntaxes are exactly like jquery. .
The reasons for those will be clear soon enough. . . . . . . .i wish to release a sample code at
this point, but since the source code will be useless, so i wont bother now. . . . . . . . , . . . . .
Re: :: Dhtml Framework Evolution by Nobody: 6:58am On Aug 07, 2009
Frontend development is complete, remaining 2 things:
- ajax functionalities
- animation effects
The frontend javascript functions support roughly 85 - 95% of core jquery library functionalities. So if you are
a jquery user, you can still use stuffs like $(document.body).click({function () {$(this).css({color:'red',background:'yellow'})}});
And i think all jquery filters are supported (at least almost all).
The total uncompressed file is about 54Kb without any compression, i just need light-weight animation/ajax functionalities.
One advantage to this frontend is that, you may decided to split it up. For instance, the 54kb stuff i mentioned is contained in
about 3 - 5 files. In whatever you wish to do, you may decided to remove the areas you do not need, to save downloading time.

All these will be explained later in the documentation. I wish to add some of the backends together before releasing the first demo.
Which will give an idea of where all this is driving towards. By the way, i am not tryin to re-create jquery, as you will find out later.

I am tryin to optimize stuffs, and reduce download time for the average naija developer, who need to wait like forever for a 100KB
javascript to download. . . .

See you guys later. And as always, there are client stuffs to be done - which is slowing development (but of course, i cant complain)
Re: :: Dhtml Framework Evolution by Nobody: 7:15am On Aug 07, 2009
And that reminds me, plugins can also be created for the frontend which is exactly the same way it is done is jquery with the extend and extend.fn functions. But the frontend does not support jquery plugins yet (but can be made to support some in future). But it is not a replacement for jquery.
Then thing is that, i need some functions at that frontend which will interface with the backend later.

With regards to conflicts, this library too provides the noConflict functionality found in jquery to avoid problems with other libraries using the $ functionality to access there functions.

I was thinking that if i just add those interface functions straight into jquery like that, the file size of everything may be too much, so what i did was to make a lighter version of jquery (literarily) which i suspect will serve my purposes later. Reason being that i love lightweight, and i find jquery too packed atimes. But that having been said, i will convert my important javascript libraries to the format that will support both jquery and this "vquery".

But some will not necessarily work on both sides. Depends on the function of the plugin in question.
Re: :: Dhtml Framework Evolution by Nobody: 2:20am On Aug 09, 2009
[Update]
The framework is made up of a frontend and a backend. The frontend requires a framework like jQuery as part of it, and also some other scripts.
So to make things better, i decided to write a lighter version of jquery and call it another name - vQuery. So this vQuery is just a subset of the
frontend, and possibly may have plugins to complete the frontend later on.

Let us see a sample of what this vQuery can do right here: http://vquery.mwebng.net/
vQuery is almost complete, just remaining the ajax plugin which i will sort out later. I have other work to do, see you folks later.
Re: :: Dhtml Framework Evolution by yawatide(f): 10:50am On Aug 09, 2009
hmmm, if backend is what I think, maybe you should reconsider - I would say 99% of plugins out there are meant for plug-and-play - download, read the instructions and install. Sure, there can be a backend (php and/or database) but considering what most are used for (animation, etc), there is no backend involved.

Also, be unique. Why vQuery? When jQuery came out, the maker didn't name it after scriptaculous or prototype or ruby though it might be based on those. People might have dumped it in a heart beat if he simply modified the name. He came up with a unique name. hint, hint.

good luck!
Re: :: Dhtml Framework Evolution by Nobody: 11:15am On Aug 09, 2009
The name vQuery is very very temporary, and everything is very subjected to change. The name backend here does not mean
plugin or content management system, it is ehm, i find it difficult to describe here, but when i get it started i will post it here.

Lemme try to explain the backend a little here. This entire system is mainly for times we need to handcode, just like jquery has
helped us shorten javascript coding. Lemme give a little scenario of a user registration system:
- You create the html form (front end)
- Create a javascript validation (frontend)
- Create fields in the database (backend) based on form data
- submit the form, with server sided validation
- save the form data into your dbase tables

Now that is a very common operation. Now all these can be done in a semi-unobtrusive manner if you have a system that
can synchronize everything together. The catch is that, it can be done unobtrusively without really disturbing your coding
pattern, whether it is dreamweaver or Notepad++. This describes the entire framework in a nutshell. I am not replacing
joomla or even wordpress.

So the framework will have 3 parts: frontend (vquery/jquery), backend (possibly php/pear), and interface between both
front and back (possibly xml/json), and i am still looking for how to add php smarty as well.

I will move the whole project to my new website: www..com later on. I intended to use jQuery for the stuff before
and my other plugins for the project were done with jQuery, so when i made a lighter version of jQuery, i just renamed the
jQuery reference in my plugins to vQuery and they all worked 'cos i have added all the common jQuery functionalities i use.

More comments please. I will come up with a name later on, for now, i will leave it at vQuery while still thinking, since it is just a
subset of jQuery.
Re: :: Dhtml Framework Evolution by yawatide(f): 11:36am On Aug 09, 2009
okay o! Though you have confirmed that it will have a backend when you said there is a database installed.

good luck all the same
Re: :: Dhtml Framework Evolution by Nobody: 11:50am On Aug 09, 2009
I am not too good at describing, besides, i like to do action first, then words later. But what i am driving at is that, this whole process
will allow both average users and pros to automate various tasks and yet will allow then to preserve their coding patterns. So if you
make use of frontpage to develop, no problem, dreamweaver. . . .lemme delve a bit more. An object such as a form is created (in the frame
work format) and can passed as reference to both frontend and backend for various levels of processing, both frontend (jscript), backend (dbase creation, validation, submission, then later rendering). So this is going to involve lots of things later on like .htaccess files, xml, json and many
of our other dhtml buddies. . . .it is time to party.

Forms are just about the best way to describe it. But having said that, there are still some other stuffs that will be injected in later. Like the frontend supporting internet explorer behaviour files (.htc files) on a crossbrowser level (at least the regular desktop browsers) - for those that understand.

What i am doing is not entirely new, i am just combining many open source + personal experience together, hoping to make some sense
Re: :: Dhtml Framework Evolution by Nobody: 11:34am On Aug 11, 2009
I have completed the ajax plugin that support all the important ajax calls, and i am using the ajax queuing method rather than
ajax threading (which is rather complicated). . .i am yet to feature this new script stuffs in any site yet, so i guess it is still in
trial mode. . . pending proper documentation (photocopy of jquery api plus my own salt 'n pepper). . .
By the way, the ajax plugin i made is about 4-5 Kb uncompressed, and probably 2KB when compressed. Because of that, i am
thinking of just adding it directly into the core library itself, and leave the animation outside. When i have more time i will rewrite
the animation module to reduce the size by over 50%, but the commands/functions will not change. . .see you folks later
Re: :: Dhtml Framework Evolution by Nobody: 8:49pm On Aug 11, 2009
More changes:

Effect demo:  http://vquery.mwebng.net/ [modified slightly]
Ajax demo 1: http://vquery.mwebng.net/ajax.html
Ajax demo 2: http://vquery.mwebng.net/ajax.html

File Size [Unpacked]
vquery.library.js  -  57KB
vquery.ani.js       -  13KB
vquery.ajax.js     -    5KB

File Size [packed]
vquery.library.min.js  -  23KB
vquery.ani.min.js       -   7KB
vquery.ajax.min.js     -   3KB

The core library can run standalone in situation where you do not need to use the ajax or animation effects, though it support
load/hide and the getScript function.
I have provided backward compatibility for all the jquery functions used in this project 'cos i have extended some of them.

[Updates to come]
I still want to add the $.ajax function and the $.ajaxSetUp functions later before i can say i have completed the ajax function.

As for the animation, i will upgrade that package letter to support color animation, text tweening, and sequencing animation.
But i will leave those ones for now, it is not an essential part of this project.

[After the vQuery stuff]
I will get to the backend/php processing aspects, and then do the interface aspect which is where all this is driving at.
Just that the frontend is very important in all of this. I wish to separate my scripting stuffs from my main site.
So i will move all these framework stuffs to www..com later on  and leave www.mwebng.net as my personal/customer
website while that like the name is going to be my geek site!

[Feedback]
Comments, suggestions, criticisms and all are welcome o!
Re: :: Dhtml Framework Evolution by Nobody: 5:38am On Aug 14, 2009
Well. . . . . .no replies yet?
Re: :: Dhtml Framework Evolution by Nobody: 5:05am On Aug 15, 2009
Well, after the short break with joomla and others (which was needed to handle a rather difficult task), i am back to my framework.
So now that the frontend is almost complete, we get to the backend.
Now this backend will feature things like this:
- Easy creation of template. The model here is similar to MVC of joomla, dat is wat makes joomla sites to be able to switch templates
without loosin functionalities. Well, this one too is similar.
By the way, maybe i forgot to mention it, but this framework is intended for direct coding, not with joomla and stuffs.
It improves your direct coding by giving you more freedom, and reducing the codes you write.

Notice that joomla by default make use of mootools, my framework will use my vQuery lib which will be renamed shortly.
Re: :: Dhtml Framework Evolution by TechPros(m): 2:28pm On Aug 15, 2009
framework fire
Re: :: Dhtml Framework Evolution by TechPros(m): 2:29pm On Aug 15, 2009
why should i use yours when we have the likes of jquery and others
Re: :: Dhtml Framework Evolution by Nobody: 9:23pm On Aug 15, 2009
I am not asking anybody to use mine. It is just lighter to do some tasks. Even i use jQuery, and now mootools.
But sometimes, i need something really really light. Then i use this. Besides this my library will serve as my
frontend javascript library in joomla. I will add more extensions to it in as situations demand. Then again, it can
also load jQuery and any library by some internal functions, and yet, there will be no conflicts.

There are lots of libraries and frameworks all over the place, so developers have alot of options to select from.
The most important thing is to know first, what you wish to develop, then next what is the best utility!
Re: :: Dhtml Framework Evolution by Nobody: 11:30am On Aug 29, 2009
I am using the framework on a testrun of a live site at the moment.
Here is just a little info on what is behinf the scene,
building plugins for this lib is exactly the same way it is done in jquery.

And i hav made some plugins hia http://.com/framework/dev/

For those that hav seen the prototype of this library, they will notice i am now
migrating my former controls and methods into this new one.

By the way, the backend aspect of the framework is already in progress, i just need to
sort out some things before posting it here
Re: :: Dhtml Framework Evolution by Nobody: 6:57pm On Aug 29, 2009
I have not done a full test running. Just that some ppl just want to see what i have been up to. So bug reports and all that is welcome!
Re: :: Dhtml Framework Evolution by Nobody: 10:50am On Sep 05, 2009
After reading all the source codes of joomla and jquery thoroughly, i have finally been able to complete the first version of my framework.

Yep, both frontend and backend. Now the backend is rather like joomla in a way (about 70%).

Now the frontend and the backend of my framework can work independently or together. They are both extensible, so addons can be added to
increase functionalities.

The major strength of the frontend is that it is rather like jquery+mootools but wit some missin features which i sacrified because of speed.
Here in Nigeria, our internet is the fastest in the world so we need to use light weight scripts.

The backend presents a very simple interface for writing your own codes into templates, modules, components and plugins.
Some features present in CMS are also here too like:

- automatic session handling, store in file, dbase or whatever
- Has its own dbase manager and presents several dbase functions like pdo and others
- In-built cache to speed up loading of your pages
- Some common security features like preventing javascript stuffs in the address bar
- . . . , . too mush to remember. . . . .

I am using it to create a website at the time of this writing, that will help fix bugs and other stuffs. And then i will complete the documentation. . . .
Re: :: Dhtml Framework Evolution by Nobody: 10:54am On Sep 05, 2009
- stuffs like Model View Controls are applicable.
- It supports easy language translation (though i have not implemented it yet)
- Several interesting objects, some inherited from pear, some exported(cloned) from joomla

All in all, i am thinkin of a framework that will suite an average web developer that can do a little coding.

Though i still maintain that the framework support whatever style of coding you may wish to use.

To convert an existing template to that of my framework should take less than 10 minutes for the first time
and less than 5 minutes subsequent times. The template is rather similar to joomla but simpler to use.
Re: :: Dhtml Framework Evolution by Nobody: 10:56am On Sep 05, 2009
Some developers here and non-nairaland members are already proposing plugin. And in case i forgot, it is open source. Lemme finish the prototype site first before i start shooting my maut!
Re: :: Dhtml Framework Evolution by OmniPotens(m): 12:00pm On Sep 05, 2009
Just put things together then do a demo website on it and surely, people will see the different available features then be able to put up one or more questions or suggestions. I hope you get all these done and ready so soon.
Re: :: Dhtml Framework Evolution by Nobody: 12:13pm On Sep 05, 2009
I will do the demo later and documentation. First i am doing a serious-minded live site with it.
By then lots of bugs will have been thrown up and handled so that testers will have lesser work to do.
I hav a mock documentation useful only to me for now. When all is workin well, i will do the complete
documentation in pdf and CHM format later on.

In this, i have used several ideas gathered from my discussions with
- YAWA-TI-De
- nitation
- qadrillo
- webdezzi
- remoranger
- omnipotens

at least those that i can remember right now. Thanks everyone for your support. I will accelerate work
on the test site and let u guys know what's up!
Re: :: Dhtml Framework Evolution by Cactus(m): 4:09pm On Sep 05, 2009
If you have come across this before. Cool else check it out. Trying to use it for something.

http://www.glassbox-js.com/

also look at   www.ajaxrain.com for different javascript framework implementation
Re: :: Dhtml Framework Evolution by Nobody: 4:18pm On Sep 05, 2009
Thanks. I have used ajaxrain rain before. However, i presume i have already made the core of my javascript library for this framework. Other things will come in as addons and plugins. I will like to maintain the core light otherwise it will have the same problem i am having with jquery.

The other reason why i had to create a javascript library is because some features of the framework will rely on both the frontend and backend processing later on. Like a json facebook-like chat i have partially completed and other future addons.


And again, from yawatide, it is not always good to rely too much on javascript. I am creating an XHTML crossplatform framework. And still will try
to look into mobile phone wap 2.0 compatibility later on. So much things to be done.

(1) (2) (3) (Reply)

Which Is More Profitable Between A Single Niche Blog And A Multiple Niche Blog / How To Activate Airtel Talkmore 5X Bonus Credit / How To Get Countless Likes On Facebook

(Go Up)

Sections: politics (1) business autos (1) jobs (1) career education (1) romance computers phones travel sports fashion health
religion celebs tv-movies music-radio literature webmasters programming techmarket

Links: (1) (2) (3) (4) (5) (6) (7) (8) (9) (10)

Nairaland - Copyright © 2005 - 2024 Oluwaseun Osewa. All rights reserved. See How To Advertise. 72
Disclaimer: Every Nairaland member is solely responsible for anything that he/she posts or uploads on Nairaland.