On Sun, Feb 26, 2012 at 7:05 AM, Brad Phillips <[email protected]>wrote:
> I can really only speak as a user of the software, but I'm curious as to > what original parts of Aiki have been broken since the new work has been > applied? In general, I've been able to accomplish the same things in > largely the same ways as before. What I've seen in recent updates is > mostly is new features that have increased usability and slight > add-ons/upgrades to what is already there. For instance, the web installer > is great, multi-platform compatible, and has made it really quick to get a > new install going (especially on local installs, this was a nightmare for > me on my mac earlier on). Also, little things like being able to generate > a form without having to first insert a blank row (as was the case in > earlier Aiki revisions) is helping me to not have to be in the db on the > command line as much. > 1- edit in place 2- multi upload 3- auto fields on form change 4- widgets html cache those that I saw. I fixed it anyways so not a bid deal, it's just how to organize the code that need a re work > > I agree with Jon that Aiki Forms are the biggest hurdle in getting a fully > functioning site going quickly. This has proven to be the case on multiple > projects. I spent many hours last year reading between the lines and > guessing ontop of the limited wiki documentation to get up to speed with > what Aiki Forms are capable of, and I've written a small tutorial that > tries to make a dent in the understanding wall for people: > > http://www.aikiframework.org/wiki/Aiki_Forms/CRUD_Tutorial > > I see a lot of potential in the ease of use and inserting these > fully-functional forms into the flow of a site, and I have been able to > accomplish much using them in their current form, but it's clear that > others with more forms knowledge and familiarity with standard practices > and security procedures will be able to improve this feature once the > understanding with what's currently possible catches up to the number of > people using Aiki in sites. For instance, it seems many things are out of > the users control when utilizing the forms for data input. Things like > confirmation messages seem auto-generated and hard-coded in Aiki and, as > such, not configurable or style-able by the end user. > > Just my two cents :) > > +Brad > > > On Feb 25, 2012, at 10:25 PM, Jon Phillips wrote: > > > You are free to do what you want, but I totally disagree with your > > methods here. > > > > Aiki is getting better from hard work and continued releases based > > upon commercial projects we are doing, finding problems, fixing them, > > rinsing and repeating. > > > > What I read in your email below is "hey guys, the work you are doing > > is not helpful, so please wait for me to rewrite everything, and then > > I will overwrite all the work you are doing." However, let's face > > reality, you say one thing, and do another because your situation at > > present is unstable. > > > > So, why don't you just jump in and help fix bugs, fix big pieces or > > rewrite pieces in a branch and make each release better. > > > > Yet again, you are totally free to hack on a branch, but its far more > > inspiring each day I see a new bug filed, a bug closed, or awesome > > code fixes from rg1024, jcubic and so forth! > > > > I also think that overall, making new forms working well, that are not > > custom per each aiki site is way more important than even all the php > > markup discussions. Getting data in and out of aiki is by far the > > hardest part in the daily grind of writing aiki sites for clients in a > > reasonable time. > > > > So I beg you please, just work on one thing like NewForms.php and make > > that solid, or save a list of bugs and fix those. Rinse and Repeat. > > Aiki is getting better by the day. Others have thoughts? > > > > Let's work on this today: http://www.aikiframework.org/wiki/Aiki_forms_2 > > > > Jon > > > > On Sun, Feb 26, 2012 at 12:06 AM, Bassel Safadi <[email protected]> > wrote: > >> I have some extra time. since the current version of aiki was built by > me > >> without providing clear charts on how the code work and how stuff are > >> connected to each other. many of the latest changes by developers broke > many > >> parts of aiki. what I want to do is to restart aiki with clean code > base and > >> charts and documentation that shows how everything is connected. in the > >> meanwhile can keep hacking on the original branch. actually I don't any > one > >> to commit to my new branch yet. I'll move around blocks of code and > correct > >> the bugs that where created by the original design and will keep you > guys > >> updated. so by the time of the next couple of releases aiki 1 should be > >> ready with all commits that others did on the original trunk but with > clear > >> code base and aiki forms and admin panel. > >> > >> aiki 1 is here https://code.launchpad.net/~bassel/aikiframework/aiki1 > >> I didn't push anything yet. does this make since to people? I'm just > trying > >> to go around calling it aiki rewrite. but in a way it's. currently I > have > >> some extra time with no enough internet connection and the current aiki > is > >> becoming too messy for me. I want to keep everything others made but in > a > >> new code base. and until that is done will call this thing aiki 1 then > when > >> it match the current version with the new form creator we can move it > to git > >> since the bugs should be closed already and there will not be specific > bugs > >> to this yet. > >> > >> Ok? > >> > >> -- > >> Bassel Safadi | http://bassel.ws > >> Skype: i.know.sy | Global: +1-323-545-3855 > >> > >> _______________________________________________ > >> Mailing list: https://launchpad.net/~aikiframework-devel > >> Post to : [email protected] > >> Unsubscribe : https://launchpad.net/~aikiframework-devel > >> More help : https://help.launchpad.net/ListHelp > >> > > > > > > > > -- > > Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳ irc: rejon > > +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing) > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~aikiframework-devel > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~aikiframework-devel > > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
