Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

* | |

  Show Posts
Pages: [1]
1  PureMVC Manifold / Standard Version / Re: android on: August 11, 2009, 09:01:39
I would say so, but i am really not experienced enough in Java to be correct.
I am working with PureMVC in AS3 and just started to look into Android. It would be great if i could take all my knowledge about PMVC to the new platform.
Please do keep us informed on the porting progress.

Jiri
2  PureMVC Manifold / Standard Version / android on: August 10, 2009, 06:13:57
Does anybody know if someone is porting pureMVC to Android?
3  Announcements and General Discussion / General Discussion / Object pooling of notifications on: June 24, 2009, 03:04:24
I have the following case. There is a TimeProxy, which is sending a notification every 100 ms to a lot of Mediators. The notification that is send only has an int , the current time, as the note its body object.
I was wondering how to optimize this and if it was possible or advisable to create something like an object pool for the notification in this case.

Could some body shed some light on this idea.

much appreciated.

Jiri
4  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 21, 2008, 01:33:43
Rhysyngsun, does one put constants in a UML scheme? I am new to UML, but want to learn. Allready in this thread it has proven me that it is a nice way to communicate code concepts :)

Jiri
5  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 21, 2008, 01:30:53
Would it be considered good practice if I would create custom made notifiers that extends the Notification class and have them add to a proxy as responders. Like so
:
ISQLiteErrorResponder extends Notification
ISQLiteResultResponder extends Notification

function doQuery(queryString , ISQLiteErrorResponder , ISQLiteResultResponder):void
{
//do stuff and listen to the sql callback using flash eventlisteners to fire the responders
//only how to remove listeners, without having both responder know about each other
}
Jiri
6  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 19, 2008, 11:10:02
Ok, thats what you meant and yes SQlite does support it!!
7  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 19, 2008, 01:48:04
Cliff,

Good to hear that I am on the right track. Just one more question could you please explain or provide an example about this part:

Also, it would be good to provide for parameter replacement in queries with arguments. I don't see if SQLLite can do this or not, but the SQLQueryProxy could do it as an in-Proxy preparation of the query. You'd have a template property and an arguments property. In the same way that the setting of the query property triggers validation, setting the arguments property would do parameter replacement on the template from the arguments, and then set the query property with the replaced parameters, ready to execute.
8  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 18, 2008, 03:08:11
Cliff, thank your for the ellaborate explaniation. It is helping me a lot, allthough I am having a hard time to get my head around it! Can you please tell me a bit more about what you mean with this
An abstract SQLQueryProxy class would define things like a protected query property.
Do you mean by that a static var INSERT = 'INSERT INTO ....', or could you give an example?

Then I also dont really understand this in the last sentence.
The MySQLAppDatabaseProxy would set the ISQLQueryProxy implementers as responders for their calls. Mind your AsyncTokens

Here is also a new scheme, am I on the right track?
Jiri

9  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 16, 2008, 10:38:42
Rhysyngsun, thnx for having a look at it and the comment. I realize the async nature and I am working on how to deal with that. As I see it now the notifications should indeed be called by the SQLProxy . Because the SQLProxy holds a reference to the concrete Class SQLiteDatabase I probably need to addListeners to the SQLiteDatabase i.e. SQLProxy.databaseRef.addEventListener(.onResult / onError) or register a responder like it is done in the Serialization Proxy example. Somehow I cant decide which one is the best one. I feel like adding dispacthers to the SQLiteDatabase that the SQLProxy can listen to is a messy solution and that defining a responder and have it implement an interface is a much cleaner solution.
I am right on this?

Jiri
10  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 16, 2008, 09:50:54
To get things clear for myself and to practice, i did a scheme. I was wondering if someone has time to reflect on it and possible give some feedback. It is very crud, but should display my intentions.

Thank you,

Jiri
11  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 15, 2008, 07:33:11
Ok, let me see if I get this correct. Instead of programming to the concrete class SQLLiteProxy, I should program to an interface, namely the ISQLProxy.
This ISQLProxy could define methods like getConnection() , initialize() , doQuery(SQLstatement) , etc.
If i understand this correctly that means that all the database handling is done inside a concreteclass that implements the ISQLProxy. How would I then deal with the possible async nature of the queries. Do I make for every ERROR, UPDATE  ,CREATE etc a command object and register those commands

If I look at the XML example, the Async methods signature defines a responder, this implies that composition is used. So I should probably have a Proxy that holds an instance of ISQLProxy (_dbase:ISQLProxy) and program to that interface. This way _dbase can be changable.
So basically I am then following the logic AIR XML Database utility, because I also intend to use responders and eventListeners.

I need to study that utility again, being more of a flash designer it is a hard and slow process entering the arena of OOP and the whole lot :)

Jiri

12  Announcements and General Discussion / Architecture / Re: AIR - Sqlite Proxy object on: April 15, 2008, 03:43:15
Thank you for the quick reply. I came across it and am using it as a base, I just would like to figure out how to make the SQliteProxy into a reusable object, so up to a certain point I can follow the same logic as in the SerializationProxy. I am just wondering where to put the query logic and if I need to seperate that into a seperate Object.

J
13  Announcements and General Discussion / Architecture / AIR - Sqlite Proxy object on: April 15, 2008, 02:38:48
Hello list,

first-off I am a bit of a newbie to using pureMVC, but so far it feels very nice to work with. I want to make a small test AIR application to get familiar with the frame work. The app will be using the Sqlite database so I will be creating a SqliteDatabaseProxy.I am just having some design questions.

I am creating a SqliteDatabaseProxy which extends Proxy. This class has a method  initialize(databaseName:String , location:File) which checks if the db file excists if not creates is and opens a Async connection using dbaseConnection.openAsync( dbFile ), where dbaseConnection is an instance of SQLConnection. After all this, a sendNotification is called to notify observers.

Considering the fact that this SqliteDatabaseProxy is only there to establish, verify and serve a database connection, I might need another Proxy object, let call it QueryProxy, that deals with the querys like CREATE,INSERT and UPDATE.
Do I then have to give QueryProxy and instance of SqliteDatabaseProxy and then implement an EventDispatcher in the SqliteDatabaseProxy so that the QueryProxy can addListeners to the SqliteDatabaseProxy and based on that send notifications to the rest of the system.
Or do I have then SqliteDatabaseProxy and the QueryProxy communicate which each other through notifications only.
Or do I just forget about two Proxy objects and just use one that deals with everything, where in this case I give up my goal to create a re-useable SQlite class.

I hope my questions are clear and that somebody can advise me.

Jir
Pages: [1]