reposted to Dev&Hack forum Aug 9th, 12:30pm PST
I'm not a developer, and only an intermediate(?) VBA programmer for my own solutions. (Though several of those are quite involved.)
I have a question that I'd like to post on the Developers forum, because I believe it falls in "their" wheelhouse.
I've read and respect the posting guidelines published for each forum and the site generally.
I've done my web search diligence, and have posted inquiry on other sites specific to my device and the particular application(s) involved. No luck.
Am requesting permission/blessing to post the following:
Keystrokes as code?
Specifically Excel Mobile keyboard shortcut Alt-PgUp/Dn
I've created several Keystroke "routines" to minimize stylus use in Excel Mobile. I've mapped to hardware buttons, and they all work great... except Alt-PgUp(and PgDn). In Excel, these key combos will scroll one screen left or right, respectively. Other similarly-coded "routines" work as expected.
I've worked around this for now by recording screentaps in Excel's horizontal scrollbar. Unfortunately, the location of that s/b depends on whether SIP is active. If it is, the vertical co-ordinates of the screentaps become irrelevant and/or potentially destructive to my intended result. I prefer to avoid "position dependent" commands whenever possible for obvious reasons.
I have several other programs at my disposal to effect the Alt-PgUp/Dn shortcut(s).... IF I knew how to define the values(?) of Alt-PgUp/Dn in a script.
(MortScript, PHMkeys, Pen Commander, Spb FullScreenKb, PDA MediaKb)
I've been all over the web, and I think I understand keystroke scan-codes and values... and how they work together. Is there something akin to an ASCII "value" for this key combination? (099/0A1; 073/081; 153/161)?
Any ideas are appreciated. I've no aversion to research or work, but can't figure out what to ask or where to look further.
(I just really need a more direct/reliable functionality to scroll entire screen at a time left/right.)
Thanks in advance if anyone can help.
Dell Axim x51v WM5 (if it matters)
(Please feel free to "re-direct"/re-locate/modify/enlighten etc.)
pro-fit2: your post sounds like one of the very few that truly does merit going in the developer forum Please repost it there.
BTW, the solution to your problem sounds like you could just emulate scrollbar commands, rather then keyboard commands. That's fairly easy to do by posting WM_VSCROLL or directly manipulating the scrollbars in code. With that you can emulate smooth scroll, line scroll and page scroll. I wrote an app that can do that, once upon a time.
V
Scroll bar control, accessing, WM_HSCROLL
Vijay, thank you for permission and input.
Before I go further, I like the sound of your suggestion, but my code background is primarily VBA thru Excel, from which I access some minor(?) "other" things like PrintDialog, or other MS Office apps...
I'm willing to work through the API(?) to access window scrollbar controls, WM_HSCROLL (etc), but I would need a more basic start. If it's easy to generate, I'd love to see some further detail on the approach you described.
Thanks either way,
Pro-Fit
pro-fit2: apologies for being an ass, but could you open a thread in the developers forum, and I'll paste some code in.
I would open it for you, but it's better if it's opened under your member ID.
To get you started, this is a not particularly good article on scrollbar functions in vb.net. It's not VBA, but should give you an idea.
There are two ways to control the scrolling -
method 1: by sending the scrollbar a rough command to scroll up/down/left/right one line or one page. [ WM_VSCROLL with SB_LINEDOWN/SB_PAGEDOWN ]
method 2: by sending specific thumbposition control commands, which will give you fine control over the scrollbar. Frankly, this is probably what you don't need as it requires you to interrogate the scrollbar and then react accordingly. You just need to emulate line up/down I think. Look into SetScrollInfo etc.
Again, apologies for being obtuse, but there's no point filling this thread with redundant info. But start here:
http://windowssdk.msdn.microsoft.com/en-us/library/ms674659(vs.80).aspx
Open the development thread and we'll continue
V
Hi all, i don't know if it has been asked already but it would be great to have a light black&white forum "Development and Hacking" easy to load and browse from our PPCs/SPs exactly like the iPhone's app called Installer... ok, without all the "sources/install/uninstall" thing, only app name (with very short description like the one we can see if we mouseover a topic's name) and, clicking on it, the author description, link to the Dev&Hack forum article, link to the download, little screenshot or animated gif. And a tiny search engine (no Google)
I know there are websites made like that already like freewareppc or softonic which use RSS, but i was thinking about a more Installer-like webApp.
http://it.youtube.com/watch?v=j7rfU4r3Y-0
.. but there's probably something like that already, so i ask you guys and gals where can i find such a service and if you think it would be nice or totally useless
TBH this would take ages to compile and program and with every different model of HTC h/set out there I dont think anyone would have the resources or time to do this. I do really like the idea though kudos for that
Why not look at the App To Date over at MoDaCo?
livefastdiefun87, i don't think it should be that difficult to filter the threads (for example a "[release]" string in the thread title) as links to their first posts (the ones with descriptions, screenshots and downloads) to the user (maybe it's enough for the releaser to keep an eye on the format). For example A_C's releases already have the "required" things (first post: description and download, second post: faqs).
With a little help from any developer i think that even with pocket ie (although a client would be better) we can retrieve every release easier. Then, in order to explore the apps, the user can jump to the ordinary forum.
Maybe i'm making it too simple, but it wont be bad anyway. I'm thinking about a mobile-only road, no ads, no banners, black and white with hypertext
As far as I know, the only software difference between Dream and Sapphire is kernel and driver stuff, neither of which effect themes at all.
So why not get rid of the Sappire themes forums completely and just provide a link (for convenience) to the Dream ones? The Hero themes might be identical as well?
I'm sure there are a few other discussions that can be shared between the various platforms too.
I only suggest this because this website is fairly slow (at least here) and having to search both the Dream and Sapphire themes topics can be quite frustrating.
All of my Oreo themes work for CM so if you are running that version of CyanogenMod you can use my themes for the G1. The same applies to any theme, they are just built for a specific rom, not hardware.
Thankyou for clarifying that. It's exactly what I'm getting at. Dream? Sapphire? Hero? It doesn't matter regarding themes because they are all interchangeable between these models. The themes forums for all 3 platforms (and any others that are compatible) should be merged so that it's easier to locate them.
Actually some Rom's are not yet for all Sapphire builds yet. Like the Hero's. There getting there just not yet
Because if someone comes here wanting to theme their Sapphire, and theres no dedicated section for it, the average person would probably be confused, then continue their search elsewhere.
I'm sure in this day and age we have the technical capacity to still make it seem like there is a "Sapphire themes and wallpapers" section, can simply link to to the "Dream themes and wallpapers" section transparently. I agree that it would be confusing for users to not find such a section at all.
My problem is that we have parallel discussions happening, which is a waste of time. It's also a waste of time having to search 2 sections in order to prevent parallel discussions happening. Why not simply merge them since we know for a fact that all the content within such a merged forum would apply equally to both for the benefit of all?
I agree. This is confusing. There are a LOT more themes available on here than what you see in this area because themes for Magic and G1 are also compatible.
Why don't we use tags for this?
From the FAQ:
Tags
What are tags?
Tags are a useful way to search for threads with similar subject matter and content. This complements the normal search system, which searches only for certain words or phrases and/or posts by specific users.
To use tags, you add words or phrases to threads to help describe the content. For instance, if the subject matter is 'photography' then you can add the tag 'photography' to the tag list. But you could also add tags like 'digital image', and 'camera' (depending, of course, on the nature of the thread).
This will categorize this thread with all other threads that have matching tags, whether or not they have the word 'photography' in them.
Who adds the tags?
Tags are initially added to threads by the user who started the thread. Other users may also be able to add and remove tags.
How do I use tags?
Tags are displayed in a box near the bottom of a thread page. Clicking on a tag will allow you to view other threads that have the same tag - and which may be related. Clicking on the word 'Tags' in the top of the box will take you to an overview page with a 'tag cloud.'
This cloud allows you to see which tags are the most popular - the larger the word, the more times it has been used on threads within the board. There is also another tag cloud on the advanced search page that shows you the tags that have been searched for (or clicked on) the most.
Click to expand...
Click to collapse
We could post a sticky listing the tags in use to be consistent. When you post a theme, you tag it. Relevant data would be:
Type (#theme
Theme name (#remix)
OS (#android)
Compatible ROM+build (#cyanogen4.0.4)
Compatible devices (#hero #sapphire #dream)
Then search tags instead of threads.
Vallyn: that's not a bad idea really. I've noticed there's already a convention in place for the title of a thread, which is almost as good as some minor tagging. I'm actually just now transitioning my data over to tags and it's actually a really cool way of doing things.
Convincing everyone to start using the tags can be tricky though. That may or may not be easier than possibly having to modify the layout or even backend of these forums to get a simple link in. /shrug
Hey everyone,
Migrating the old wiki to the new software is a big job, and thanks to everyone that is contributing! If you want to contribute and you're not doing so already, send me a PM and I will give you the information you need to help.
This thread shall act as a central place for discussion relating to the migration of the wiki. In the end, we want the wiki to act as an information-rich, well-organized database that XDA users can refer to for information about the things we discuss most here at XDA.
P.S. I'll be keeping an eye out for the most active contributors to the migration and population of the wiki. We will need a couple of Wiki Admins after this process is complete to ensure the smooth running of the new wiki going forward. =D
DaveShaw EDIT
Attached is a wiki syntax converter.
It's in WPF and .Net 4.0 so it might need the latest .Net Framework from MS.
I'll post updates in this thread.
PM me bugs.
I'm in on this and happy to answer any phpWiki / media wiki questions.
I have a tool for converting between the syntax's if anyone's interested.
I'm just adding support for tables and then I will post it up.
I'm also trying to head up some projects and get some standards / policies on the wiki, but the main job is getting stuff over.
If you can try and follow the examples others are doing on there, we'll have a ver nice wiki at the end of it.
The [[HTC Rhodium]] page is what I'm hoping most of the structure will be, but it's a wiki, and anyone can change that.
Dave
Congrats to all the team!
A new Wiki will be very welcome
Willing to help on the Nexus one and general android article. XDA wiki is great !
Yeah I think once the Wiki is done it will look really nice! I've been doing alot of work with the devices.
Posted my wiki syntax converter (with table support) in the first thread.
DaveShaw said:
I'm in on this and happy to answer any phpWiki / media wiki questions.
I have a tool for converting between the syntax's if anyone's interested.
I'm just adding support for tables and then I will post it up.
I'm also trying to head up some projects and get some standards / policies on the wiki, but the main job is getting stuff over.
If you can try and follow the examples others are doing on there, we'll have a ver nice wiki at the end of it.
The [[HTC Rhodium]] page is what I'm hoping most of the structure will be, but it's a wiki, and anyone can change that.
Dave
Click to expand...
Click to collapse
Yeah in porting some pages over I've either noticed the old page has lots of invalid links or the page is just a mess. I agree that we should just work on getting everything over to the new wiki and then later on we can work on cleaning it all up and enforcing some standards.
The phone template is a great start. The phone pages should be named by MANUFACTURER_DEVICE_NAME instead of just the DEVICE_NAME. I've seen some pages that are not named like that or end up being re-directs of some sort to the above syntax.
We need a table class so all the tables can be standardized. I've been using this simple style to create a less ugly table
Code:
{|border="1" cellpadding="3" style="border-collapse: collapse;"
For those who are porting images over, it seems everything from the original wiki is on the new domain however files in the /uploads/ folder from the old wiki should be moved to the proper directory on the new wiki. Can we also allow some other file types in the uploader besides images? PDF, .doc, .zip?
Also it seems some pages are missing from the old wiki? I'm not sure if that is just incorrect syntax on the old wiki or not. Remember to read or post on the discussion pages if you have ideas or questions about a specific page. I've certainty been leaving some notes and questions there.
shortkud said:
Yeah in porting some pages over I've either noticed the old page has lots of invalid links or the page is just a mess. I agree that we should just work on getting everything over to the new wiki and then later on we can work on cleaning it all up and enforcing some standards.
The phone template is a great start. The phone pages should be named by MANUFACTURER_DEVICE_NAME instead of just the DEVICE_NAME. I've seen some pages that are not named like that or end up being re-directs of some sort to the above syntax.
We need a table class so all the tables can be standardized. I've been using this simple style to create a less ugly table
Code:
{|border="1" cellpadding="3" style="border-collapse: collapse;"
For those who are porting images over, it seems everything from the original wiki is on the new domain however files in the /uploads/ folder from the old wiki should be moved to the proper directory on the new wiki. Can we also allow some other file types in the uploader besides images? PDF, .doc, .zip?
Also it seems some pages are missing from the old wiki? I'm not sure if that is just incorrect syntax on the old wiki or not. Remember to read or post on the discussion pages if you have ideas or questions about a specific page. I've certainty been leaving some notes and questions there.
Click to expand...
Click to collapse
I'm naming / moving pages from [[Rhodium]] to [[HTC Rhodium]] and leaving re-directs.
If you see any pages that need deleting, bang the {{delete}} template on them and I'll take a look.
The old wiki had missing pages, if they're not there, then they are probably gone, but you can post some links and I'll take a look.
As for CSS, can you edit the MediaWiki:Common.css page? I doubt it, but I will have a look at the styles and that later, for now I am just sticking the equivalent of <table border="1"> on each table so I can see the rows.
I also know some decent wiki coders, who I'm going to ask to help me with the basics.
Dave
The User Help -> Formatting section of http://www.mediawiki.org/wiki/Help:Contents covers Tables (bottom of page) and such. I've been using the guide quite a bit while porting (migrating) the Raphael section of the wiki.
HTH,
Just been working on some of the android sections, but I noticed that Dave's wiki convertor seems to be dealing with external links wrongly.
Where, for example,
Code:
*[VillainROM 5.5.0 (2010-05-04) | http://www.villainrom.co.uk/viewtopic.php?f=23&t=402] by nprussell
is converted to
Code:
*[[ http://www.villainrom.co.uk/viewtopic.php?f=23&t=402|VillainROM 5.5.0 (2010-05-04) |]] by nprussell
this produces a broken link. However, if it were to output
Code:
*[http://www.villainrom.co.uk/viewtopic.php?f=23&t=402 VillainROM 5.5.0 (2010-05-04)] by nprussell
then it should work fine.
ie. use only one square bracket when link is external to the wiki, and instead of the pipe character between URL and title, a space should be used.
Just an observation. No idea if this is possible, feasible, desirable or even correct for anyone other than me...
EDIT: Hmm. Ignore me for now I think. I did another page and it worked fine... Strange. I'll try and see what the issue is
EDIT2: I also added the
Code:
{{Outdated}}
tag, which can be used at the header of a page to highlight it being outdated. For an example, see http://forum.xda-developers.com/wiki/index.php?title=VillainROM
anon2122 said:
Just been working on some of the android sections, but I noticed that Dave's wiki convertor seems to be dealing with external links wrongly.
Where, for example,
Code:
*[VillainROM 5.5.0 (2010-05-04) | http://www.villainrom.co.uk/viewtopic.php?f=23&t=402] by nprussell
is converted to
Code:
*[[ http://www.villainrom.co.uk/viewtopic.php?f=23&t=402|VillainROM 5.5.0 (2010-05-04) |]] by nprussell
this produces a broken link. However, if it were to output
Code:
*[http://www.villainrom.co.uk/viewtopic.php?f=23&t=402 VillainROM 5.5.0 (2010-05-04)] by nprussell
then it should work fine.
ie. use only one square bracket when link is external to the wiki, and instead of the pipe character between URL and title, a space should be used.
Just an observation. No idea if this is possible, feasible, desirable or even correct for anyone other than me...
EDIT: Hmm. Ignore me for now I think. I did another page and it worked fine... Strange. I'll try and see what the issue is
EDIT2: I also added the
Code:
{{Outdated}}
tag, which can be used at the header of a page to highlight it being outdated. For an example, see http://forum.xda-developers.com/wiki/index.php?title=VillainROM
Click to expand...
Click to collapse
Noticed the new Templates, nice work .
If you can let me know an exact line / snippet that is wrong I'll debug it. (The whole app was a Regex crash course)
It is designed to output the URL's in the format you expect .
Dave
OK. Here's one that doesn't work right.
Code:
*[Andro-Plus 1.1 (2010-02-08) | http://forum.xda-developers.com/showpost.php?p=5570560]
from http://URL to the wiki /index.php?pagename=GSM Hero ROMs
Output is
Code:
*[[ http://forum.xda-developers.com/showpost.php?p=5570560|Andro-Plus 1.1 (2010-02-08) |]]
Expected is
Code:
*[http://forum.xda-developers.com/showpost.php?p=5570560 Andro-Plus 1.1 (2010-02-08)]
I have put these on my talk page on the new wiki, http://forum.xda-developers.com/wiki/index.php?title=User_talk:Anon2122, so you can see the issue.
By using double square brackets, mediawiki is treating it as an internal link, when it should be external. If the string begins "http://", then only one square bracket should be used.
I have no idea why the phpWiki for this example had a trailing pipe within the square brackets but it can be ignored.
The pipe separating the link from the description should also be a space. The first space encountered in the square bracket is treated as the splitting point.
HTH mate,
P
anon2122 said:
OK. Here's one that doesn't work right.
Code:
*[Andro-Plus 1.1 (2010-02-08) | http://forum.xda-developers.com/showpost.php?p=5570560]
from http://URL to the wiki /index.php?pagename=GSM Hero ROMs
Output is
Code:
*[[ http://forum.xda-developers.com/showpost.php?p=5570560|Andro-Plus 1.1 (2010-02-08) |]]
Expected is
Code:
*[http://forum.xda-developers.com/showpost.php?p=5570560 Andro-Plus 1.1 (2010-02-08)]
I have put these on my talk page on the new wiki, http://forum.xda-developers.com/wiki/index.php?title=User_talk:Anon2122, so you can see the issue.
By using double square brackets, mediawiki is treating it as an internal link, when it should be external. If the string begins "http://", then only one square bracket should be used.
I have no idea why the phpWiki for this example had a trailing pipe within the square brackets but it can be ignored.
The pipe separating the link from the description should also be a space. The first space encountered in the square bracket is treated as the splitting point.
HTH mate,
P
Click to expand...
Click to collapse
Thanks I'm just looking at another URL conversion problem at the moment .
Might be the same root cause, phpWiki is very forgiving in allowing shocking markup.
Dave
DaveShaw said:
Thanks I'm just looking at another URL conversion problem at the moment .
Might be the same root cause, phpWiki is very forgiving in allowing shocking markup.
Dave
Click to expand...
Click to collapse
Yeah, seems so. It's no hassle to change them manually, as I've done for most of the hero stuff i can find, but it gives you a RegEx challenge
There should not AFAIK be a pipe at the end of the URL in phpWiki, so I have no idea how that got there
Cheers
anon2122 said:
Yeah, seems so. It's no hassle to change them manually, as I've done for most of the hero stuff i can find, but it gives you a RegEx challenge
There should not AFAIK be a pipe at the end of the URL in phpWiki, so I have no idea how that got there
Cheers
Click to expand...
Click to collapse
I know what it's meant to look like, it's the Greedy Regex Expressions that are changing it for me.
I've changed the whole URL stuff and am just trying to cobble a new feature in before bed.
Dave
Changes to the Syntax Converter:
- Improved URL / WikiLink Parsing. Fixed bugs reported by anon2122 and Captainkrtek.
Stuff Todo:
Code:
//TOOD: URLs with Spaces!
//TODO: Remove Braces from URLs for Images.
//TODO: Add File: prefix for WikiLinks for Images.
New Version is : phpWikiConverter (1.0.3853.42492).zip
DaveShaw said:
Changes to the Syntax Converter:
- Improved URL / WikiLink Parsing. Fixed bugs reported by anon2122 and Captainkrtek.
Stuff Todo:
Code:
//TOOD: URLs with Spaces!
//TODO: Remove Braces from URLs for Images.
//TODO: Add File: prefix for WikiLinks for Images.
New Version is : phpWikiConverter (1.0.3853.42492).zip
Click to expand...
Click to collapse
Thanks! this tool has been great, glad to have the links fixed, time to re-convert a bunch of pages
Thanks DaveShaw!
Devices list
Hey Everyone,
You've probably found this already but its very useful for filling the devices template
http://en.wikipedia.org/wiki/List_of_HTC_phones
Cheers!,
Captainkrtek
Hey all, I am new here, but not to wiki.
I have a question about approriate content on the new wiki. An example would be Gene_Registry on the old wiki, sorry I am new and cannot post links.
Is this something that should be in the new wiki? If so I would think it should go on the Gene wiki page.
click23 said:
Hey all, I am new here, but not to wiki.
I have a question about approriate content on the new wiki. An example would be Gene_Registry on the old wiki, sorry I am new and cannot post links.
Is this something that should be in the new wiki? If so I would think it should go on the Gene wiki page.
Click to expand...
Click to collapse
I'm liking subpages at the moment. But I'm not sure if it's the best way forward.
i.e. http://forum.xda-developers.com/wiki/index.php?title=HTC_Gene/Registry
But if you want to keep the old page name to save time that's fine, the main aim is migrating content at the moment.
Dave