I always look at projects, mine or others, with a little nostalgia.
I also dream big. In the world of programming its hard not to have
someone else steal your programming ideas too… but if its open source
its ment to be shared.
Anyway here is what I have been thinking but understand nothing is set in stone.
the 1.5.x line may get some extra features… I was even thinking of reintegrating the newest version of phpmyedit (5.7.1) back in… but it isn't php 5 ready, and it has been rewritten using php classes so it would be a bunch of work to learn how the software works before integrating the php 5 ready 1.5.x with their non-php 5 ready…. it feels like I am just making a "front end" using other peoples work… but thats my thoughts on that.
for a 2.x and 3.x I have thought of taking the phpmyaccess code base plus the 2.x and 3.x phpmyAdmin codebases plus some other cool code I'm working on and marrying them all together…. that is a possibility as well.
Then there is the Concept of a phpMyAccess complete rewrite to do just exactly what it sounds like: a MS Access looking interface for MySQL using LAMP. That is the way I am leaning.
I have been working on mockup views of different interfaces, and working on some super cool stuff:
File, edit, view… AJAX pulldown menus
AJAX right click menus
Query "Design" view
Concept: how to save Queries, then reload them into "edit" design view
I will keep posting as I go to let you all know how its coming and what direction the development goes.
I'm considering putting up Git or svn but my dev environment is currently Adobe Dreamweaver CS5 for MAC
and I'm trying to find a easy way to integrate that into my workflow. I heard there was a way to integrate one of those with
Dreamweaver CS5 on Windows, but it doesn't work with MAC…. oh well… any help on this would be appreciated.
Now you all know what I'm thinking and hopefully that will keep you all tuned in as the dev goes.
gfdos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Completed:
Create a window that shows a list of Existing Queries
Create a subwindow that allows you to "design" and save them.
Create a function that will update list of Existing Queries after a new one has been created
WIP:
Create a way to create "New" queries regardles of which query is selcted
Create a way to select queries from list (so Open or Design can be run on them)
Create a way to "design(edit)" them in subwindow - parses sql queries back into design form.
Create a way to run them (input into access table view)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Weekend was super busy, but I got some sleep and now looking at code with fresh eyes.
Completed:
Create a way to select queries from list (so Open or Design can be run on them)
Create a way to run queries(v1, static table - dynamic table = future dev)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Completed:
Check for Selected Query. Run Query or return warning "No Query Selected"
Create a way to create "New" queries regardles of which query is selcted
Create a way to "design(edit)" queries in subwindow - parse sql queries back into design form.
Update runquerypost() interface for ajax (input into access table)
Found 4 bugs, javascript traps firing and not reseting. As soon as I can get that fixed, I got a few more features to add and then I'd like to get this out in alpha. Understand: Its still bleeding alpha…. not ready for prime time, but I think many will enjoy at least this preview…. At this point just the Query Creation/edit/run are in place, and there is NO parsing/translation/functions for MS Access like "function" support, but it is coming along nicely.
gfdos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Time away from the code and sleep helped. Looking with fresh eyes… fixed BUG 1 through redesign.
Applying that redesign to BUG 4.
Fix for BUG 1 has aided the Development goal of allowing each saved query to be run and displayed in a window, re-running will take over that window.
Fix for BUG 4 is simply applying this Dev to the concept of Editing a saved query… so multiple queries can be edited, each in their own window… if a query is attempted to be re-edited while it is already being edited, it would take over that window - so need to add some Dev here too, throw warning if that happens.
BUGS 2 and 3 are next - these are from integrating code that was "run once" elsewhere…. have to make the code "multi-instance aware".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BUG 3 Resolved…. Had to make window controls multi-instance aware… Rewrote all the functions for multi.
KNOWN BUGS FIXED!!!!
Back to Dev Road map:
Add features:
Queries: Save(overwrite rather than just Save as)
Queries: Delete
Implement Right Click
-Prep for Alpha Release-
gfdos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Working on rewriting all code for Query Design Windows - there are 3 types: new, confirm, standard.
Need to use seperate arrays rather than associative arrays with the 3 types in side it - Javascript doesn't like Associative arrays!!!
Found this wile working on Queries: Save(overwrite rather than just Save as) -- because I wanted a custom confirm box rather than just Ok/Cancel. This is not a new request, but I dont want someone elses that has 500 of its own custom css types added…. I want it to be just simple…. and I think I've got it… I'll just implement another window with buttons in it… then call appropreate class calls to close what I dont want open at the end of it all - to do that I need to not just close windows, I need to pop dhtmlwindow objects off their respective arrays…. thats how I found out Associative arrays are no-nos in javascript.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Additional feature requests added to dev map prior to alpha release.
Add ability to edit in query window
Add method to export… (html table using runquery non ajax version?)
Add method to export… (to excel using export routines from phpMyAccess 1.5.1)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I always look at projects, mine or others, with a little nostalgia.
I also dream big. In the world of programming its hard not to have
someone else steal your programming ideas too… but if its open source
its ment to be shared.
Anyway here is what I have been thinking but understand nothing is set in stone.
the 1.5.x line may get some extra features… I was even thinking of reintegrating the newest version of phpmyedit (5.7.1) back in… but it isn't php 5 ready, and it has been rewritten using php classes so it would be a bunch of work to learn how the software works before integrating the php 5 ready 1.5.x with their non-php 5 ready…. it feels like I am just making a "front end" using other peoples work… but thats my thoughts on that.
for a 2.x and 3.x I have thought of taking the phpmyaccess code base plus the 2.x and 3.x phpmyAdmin codebases plus some other cool code I'm working on and marrying them all together…. that is a possibility as well.
Then there is the Concept of a phpMyAccess complete rewrite to do just exactly what it sounds like: a MS Access looking interface for MySQL using LAMP. That is the way I am leaning.
I have been working on mockup views of different interfaces, and working on some super cool stuff:
File, edit, view… AJAX pulldown menus
AJAX right click menus
Query "Design" view
Concept: how to save Queries, then reload them into "edit" design view
I will keep posting as I go to let you all know how its coming and what direction the development goes.
I'm considering putting up Git or svn but my dev environment is currently Adobe Dreamweaver CS5 for MAC
and I'm trying to find a easy way to integrate that into my workflow. I heard there was a way to integrate one of those with
Dreamweaver CS5 on Windows, but it doesn't work with MAC…. oh well… any help on this would be appreciated.
Now you all know what I'm thinking and hopefully that will keep you all tuned in as the dev goes.
gfdos
I'm working on the interfaces for Creating Queries.
Next up -> save the queries, reload and edit the queries.
Mabey I'll even get some "alpha" screenshots up if anyone is interested.
I've got the query creation, and saving working.
Now I have to refresh the list of queries on the main screen.
Next up -> reload and edit the queries.
Completed:
Create a window that shows a list of Existing Queries
Create a subwindow that allows you to "design" and save them.
Create a function that will update list of Existing Queries after a new one has been created
WIP:
Create a way to create "New" queries regardles of which query is selcted
Create a way to select queries from list (so Open or Design can be run on them)
Create a way to "design(edit)" them in subwindow - parses sql queries back into design form.
Create a way to run them (input into access table view)
sometimes javascript makes me want to pull all my hair out…. except my hair is divs and they are hidden. LOL
WIP:
Create a way to run saved queries (getting data from one hidden div to show inside another div)
Weekend was super busy, but I got some sleep and now looking at code with fresh eyes.
Completed:
Create a way to select queries from list (so Open or Design can be run on them)
Create a way to run queries(v1, static table - dynamic table = future dev)
Here's a piece of gold for anyone who might need it:
document.form.elements.selectedIndex = x;
doesn't work
You have to add "id=" tags to your <select> elements and then do this:
document.getElementById("dropdownname").selectedIndex=x;
(At least in Chrome or Firefox…..)
They look similar, and in theory should do the same thing… but they don't.
Okay back to programming!
Completed:
Check for Selected Query. Run Query or return warning "No Query Selected"
Create a way to create "New" queries regardles of which query is selcted
Create a way to "design(edit)" queries in subwindow - parse sql queries back into design form.
Update runquerypost() interface for ajax (input into access table)
Found 4 bugs, javascript traps firing and not reseting. As soon as I can get that fixed, I got a few more features to add and then I'd like to get this out in alpha. Understand: Its still bleeding alpha…. not ready for prime time, but I think many will enjoy at least this preview…. At this point just the Query Creation/edit/run are in place, and there is NO parsing/translation/functions for MS Access like "function" support, but it is coming along nicely.
gfdos
Chasing and squashing javascript code bugs is like blind person watching a horror movie with the sound muted.
RAID is more than just a javascript programers hardware array.
gfdos
Still fixing 4 bugs… one fix will eventually win and get applied to all 4 bugs.
Almost done with Bug 1…. nasty little javascripts!!!
midnight bowling to relax. Give me some fresh eyes on those bugs!
Time away from the code and sleep helped. Looking with fresh eyes… fixed BUG 1 through redesign.
Applying that redesign to BUG 4.
Fix for BUG 1 has aided the Development goal of allowing each saved query to be run and displayed in a window, re-running will take over that window.
Fix for BUG 4 is simply applying this Dev to the concept of Editing a saved query… so multiple queries can be edited, each in their own window… if a query is attempted to be re-edited while it is already being edited, it would take over that window - so need to add some Dev here too, throw warning if that happens.
BUGS 2 and 3 are next - these are from integrating code that was "run once" elsewhere…. have to make the code "multi-instance aware".
Work continues on BUG 4, including a redesign of Query saving to be aware of multi-queries being created/edited in different windows at the same time.
Cleaning/Sanitizing the code up a bit… indentations…. multiple remmed alert traps that needed cleaning up.
Good progress today!
gfdos
BUG 4 fixed, with a number of dev planned things fixed along the way.
Work continues on BUG 2&3. Looking forward to going back to Dev… getting a few more features in and releasing alpha soon.
BUG 2 fixed.
BUG 3 is again multi-instance related….
BUG 3 Resolved…. Had to make window controls multi-instance aware… Rewrote all the functions for multi.
KNOWN BUGS FIXED!!!!
Back to Dev Road map:
Add features:
Queries: Save(overwrite rather than just Save as)
Queries: Delete
Implement Right Click
-Prep for Alpha Release-
gfdos
Found out today that Associative arrays don't really work right in javascript.
Have to go back in and fix a few things because of this.
http://www.hunlock.com/blogs/Mastering_Javascript_Arrays
see "Javascript Does Not Support Associative Arrays"
Working on rewriting all code for Query Design Windows - there are 3 types: new, confirm, standard.
Need to use seperate arrays rather than associative arrays with the 3 types in side it - Javascript doesn't like Associative arrays!!!
Found this wile working on Queries: Save(overwrite rather than just Save as) -- because I wanted a custom confirm box rather than just Ok/Cancel. This is not a new request, but I dont want someone elses that has 500 of its own custom css types added…. I want it to be just simple…. and I think I've got it… I'll just implement another window with buttons in it… then call appropreate class calls to close what I dont want open at the end of it all - to do that I need to not just close windows, I need to pop dhtmlwindow objects off their respective arrays…. thats how I found out Associative arrays are no-nos in javascript.
Removed all Associative Arrays….went with multiple arrays instead…
Got "Save As…" working for new Queries, and am working to apply that code to Existing queries… with overwrite (Update rather than Insert)
Work continues on Existing Queries.
Save and Save as features complete.
Additional feature requests added to dev map prior to alpha release.
Add ability to edit in query window
Add method to export… (html table using runquery non ajax version?)
Add method to export… (to excel using export routines from phpMyAccess 1.5.1)
Got edit in query window working… need to do a little more to make it completely generic tho…. working with test data.
Ran a bunch of test data through it…. came up with 4 tweeks/features to add.
Working on it today, hope to get through it all!
1 of 4 completed…. still working.