Input Managers (little plugins) in Leopard don’t work when they’re not setup correctly. Making them work again can be a difficult task involving the Terminal.
So I decided to create a little utility called Input Managers which does all the fixing for you.
Step 1: Open Input Managers and click theFix button
Step 2: Enter your password (you must be an administrator)
Step 3: done 
Download Input Managers its free.
→ 2 CommentsTags: Input Managers
Ok, this is a partial update…
Although multiple accounts should work it still is unstable it may result in data duplication and it is also possible you will see only a subset of you HR contacts in AB.
I advice you to make backups and to only use this feature if you don’t depend upon your Address Book.
→ No CommentsTags: Private Beta · Greatascent
As some sources report the InputManager system will disappear in Leopard:
Greatascent greatly relies on the InputManager system to inject functionality into applications like Safari and Address Book. So this is a HUGE problem as this makes Greatascent nothing more then a synchronization client.
The only good solution is to write some kind of a replacement for the InputManager system. Many approaches are possible. For instance I could write phony plugins for Safari, Address Book, Mail and iCal or I could use APE. The phony plugins are not a good option as this approach would limit Greatascent to applications that have some kind of a plugin architecture. APE is not a good option either because I don’t like it’s interface (it is far to techie) and it has some odd licensing scheme (it’s not really free).
So I decided to write my own Code Injection system, Yet Another Plugin Architecture (YAPA).
YAPA will have a similar approach to APE’s but it will have a better UI and better non-geek interaction.
But maybe the most important feature would be the Plugin Verification System which will verify the authenticity of the plugins installed to prevent bogus plugins from taking control over your system or your passwords.
I don’t blame Apple for removing the InputManager system because it IS really easy to write some kind of spyware with this system. But we can always try to have a better approach to the problem. I think verification of the installed and loaded plugins by a trusted source is a better approach than just leaving the door wide open.
I will continue to develop Greatascent so don’t worry. I just need to make sure my work is useful and without some kind of a system wide plugin architecture my work is absolutely useless.
→ 5 CommentsTags: Private Beta · Greatascent
Create a new note:
Create a new task:
→ No CommentsTags: Private Beta · Greatascent
It’s been a few days (10 to be exact) since the last update and people are asking me why I don’t come with a new update to solve many of the bugs present.
Well, it’s quite simple I want the bugs smashed so I’m holding back any updates until at lease the duplication bug and the deleted AB contacts bug are gone.
Don’t worry. The update will be there very soon. I don’t know when exactly as I only have about 4 hours a day to work on GA (you know, I have a daytime job too )
I will change to public beta mode when the bugs (see above) are fixed and tested.
Any one will be able to get a copy so that the more subtile bugs can be found.
As some of you may know I’m a solo developer and more importantly I’m only 20 years old.
I love to develop/design software and I have a sickening passion for cutting-edge technology.
But I don’t know any thing about business, accounting, liability, etc.
So I guess I need some help here.
If someone is interested in giving me some advice (or more practical help) I would greatly appreciate it.
To be honest, I don’t know. I’m thinking about a one time fee equal to (2 x 24) = 48,00 USD this is what you pay for 2 months with a Basic account.
Keep your eyes open for the next update!
→ 2 CommentsTags: Private Beta · Greatascent
