http://api.flickr.com/services/rest/?method=flickr.people.getPublicPhotos&api_key=c125a5fda4ab0040413aa6596e716938&user_id=80063565@N03&per_page=250&format=json Flickr provides that so i can put it in the screen data URL. I put that in jsonlint.org and it comes up with an error Parse error on line 1: jsonFlickrApi({ ^ Expecting '{', '[' Is there a way i can fix this JSON and have it work since flickr keeps getting it wrong?

Try stripping out the jsonFlickrApi( and the ending ) later in the file! Mark

Hi ceerup, Mark is right. If you copy the right part of the json output you will see that it validates: { "photos": { "page": 1, "pages": 1, "perpage": 250, "total": "4", "photo": [ { "id": "7177994579", "owner": "80063565@N03", "secret": "fa3f3dd3d8", "server": "7214", "farm": 8, "title": "vitogenovese", "ispublic": 1, "isfriend": 0, "isfamily": 0 }, { "id": "7363135570", "owner": "80063565@N03", "secret": "7c3931d801", "server": "8019", "farm": 9, "title": "John Gotti", "ispublic": 1, "isfriend": 0, "isfamily": 0 }, { "id": "7355354816", "owner": "80063565@N03", "secret": "ee1132bec0", "server": "8148", "farm": 9, "title": "Paul Castellano", "ispublic": 1, "isfriend": 0, "isfamily": 0 }, { "id": "7355327222", "owner": "80063565@N03", "secret": "30bac39466", "server": "7088", "farm": 8, "title": "Carlo Gambino", "ispublic": 1, "isfriend": 0, "isfamily": 0 } ] }, "stat": "ok" } Best Regards, Danny

thanks guys, the json is valid, i put it in dropbox, the image gallery doesnt like JSON i guess because the app crashes when i click on it...sigh

Well, it has to be JSON with tags that buzztouch code understands. It can't be just any JSON at all. buzztouch expects certain fields with certain types of information. Check out the v1.5 documentation (linked on the How-To page) in order to understand what it wants. Mark

Ok will check it again Thanks Mark

Okay so buzztouch doesnt understand just "id" so i would put "itemId" for it to understand that correct?

Ceerup, perhaps it you took a step back you'll see what's happenings. Buzztouch doesn't just take JSON and convert it into screens. The XML files in your Source Code in combination with the JSON data is what Buzztouch uses to dynamically create the screen you see in the apps. So unless you have a XML file that can use the JSON data you'll not get what you're trying to create. Fred

Is there a way i can take data from a working BT 1.5 image gallery and post it in a 2.0 image gallery? Because everyone is using flickr and screen data URLs but its all for 1.5 and no one can succesfully help me with 2.0

I think it's a 2.0 thing as it works just fine as-is in 1.5 for myself and a few others. Where are you putting the code Ceerup? Into the gallery data URL?

yes its in the gallery screen data URL. And it crashes everytime i click on the image gallery

You need to check the BT documentation to understand exactly what it's expecting. You may be able to convert some of Flickr's JSON by just changing the variable name. Some of the items they provide won't be of any use unless, like Fred mentions, there is BT code to handle it and an XML file to address the layout. Mark

That makes sense to me. The only thing that doesnt make sense is, as MacApple mentioned, he pasted the screen data url JSON from flickr and it worked fine for 1.5 and was understood by buzztouch.

Well, the main difference is that the Image Gallery plugin isn't provided by BT, right? So, there may (and probably are) be differences in what JSON is expected. Mark

Oh yea..I totally forgot about that part.

Damn, see? I haven't played with BT2.0 yet, assumed or thought this was a native BT thing. We have wasted our time @Ceerup and is a large part of why I am not ready to use 3rd party Plugins. Wish I'd known, my bad. Maybe we should keep non BT plugin issues in the sites they come from, I dunno. Gutted for you @Ceerup. Where did the plug in come from?

buzztouchmods.com

@Ceerup how long did we spend yesterday, the three of us?

Is there a way i can create a gallery using 1.5 and including that somewhere in my project for 2.0?

I agree with @MacApple...support for not BT plugins should be restricted to the sites they come from. That's no statement about their quality or anything...but since this forum is dedicated to buzztouch issues, we generally approach it thinking everything is buzztouch code. At least I do. Mark

Gutted mate. I knew @Ceerup and @Alex@TM were struggling with this and spent a good two hours yesterday getting @Alex@TM up and couldn't figure out why @Ceerup was stuck. Feel stupid now. Off to walk dog.

The gallery plugin "was" a Buzztouch plugin but was removed due to unspecified issues. @ceerup, what you're wanting to do is create "child items". If you read the "readme.txt" file for the plugin you'll see how to create the JSON for the child items. You should also read the Buzztouch 1.5 documentation. Fred

'was' = 'isn't' and has been botched together, repackaged by folk other than BT hence not working the 'BT' way.

okay ill try the child items way

child items not working, i give up on the image gallery til Buzztouch comes out with a plugin

Or you could shift the discussion over to buzztouchmods.com, where you got the plugin, and get support there! Somebody must have it working...releasing a plugin that has not been tested and verified to work is bad coding for sure! (Not saying they did that at all...I'm sure it works...just need to find out how to interact with it)

i tried taking it over there, no one answered me...its okay, ill be patient , thanks everyone for all your help.

Shocker! Sorry about all this @Ceerup.

its okay MacApple. The funny thing is that it used to work like a couple of days ago, and it just stopped. but i wasnt using JSON i was using just image urls. but that doesnt work either.

That makes sense.

Hi I agree with you guys (partially), On btmods is room enough to ask your questions. But to help ceerup: When you go into the gallery you've created (in bt cpanel) look in advanced properties for screen data url. Use the url you posted above in this thread: http://api.flickr.com/services/rest/?method=flickr.people.getPublicPhotos&api_key=c125a5fda4ab0040413aa6596e716938&user_id=80063565@N03&per_page=250&format=json and click save. Go into your app en test. I just tested this and I see the images in my gallery. So don't paste the json in a file and put that file on dropbox (or somewhere else) because that doesn't (seem to) work. The code in the plugin is specifically written to make use of Flickr. Hope this helps and if you have any questions feel free to contact me or use the tools to ask questions on btmods. Best Regards, Danny

i did that. PSMDanny are you on bt v1.5? because 2.0 doesnt work when i do that

Hi Ceerup, Please send me a pm where we can discuss any further. But for now: I'm using this on 2.0 and use the plugin that Buzztouch released at the time of bt 2.1.17 (I guess). They must have their reasons to not distribute it anymore since the new website but a lot of people where using it before with good results (I also never had any problems with it). So the version that is on btmods is untouched and not modified (as far as I know). Best Regards, Danny

PSMDanny I know it isn't all down to you but if BTM release mods / plug-ins they should be supported on BTM as that is what users expect. @Ceerup asked for help on there and got nothing. I see BTM posting on here offering hosting and BT 2.0 setup so it isn't really the best ad for business if users get zero support. Not getting at you just saying, you know? This was all my fault for assuming I was working with BT code, one user it worked the other it didn't, I spent a couple of hours helping. 'works for some, not for others' means it has issues and would explain why it got pulled.

its not your fault MacApple, i should of known better, but it was false advertising saying it was made by buzztouch when it wasnt

MacApple, I understand what you are saying but lots of people just don't ask questions on the sites of other suppliers and they go straight to this forum. This forum is great and the response-time on a question here is very fast. People expect this behaviour maybe everywhere and if they don't get an answer in a minute they go over here. Again I know what you mean but have a look at the questions asked on btmods and you'll see that most of the questions where answered there or continued/solved here at buzztouch. Only thing I can say is that we (I) do our/my best to help anyone with questions. Best Regards, Danny PS For me it's not a business. In the past I converted some existing plugins to 2.0 and offered it to btmods. That's my part. Nothing more, nothing less

@ceerup, no false advertising involved. Blame the text editor, still not used to it changing.my words. Fred

lol @ calling me creepy Fred. It said it was made by Buzztouch

@ceerup, it was, but as I noted above, It was pulled for unspecified issues. Many use it without problem. Fred

It WAS made by buzztouch. I downloaded mine from bt ages ago, then it was no longer there. Haven't spotted any explanations why it was pulled. Would be interesting to know. Maybe security issues?

It was made by BT but pulled, good enough for me, but it is no longer offered by BT so to call it a BT product without saying BT no longer offer this though and we don't know why but decided we'd offer it instead..... In this case he did ask and got nothing though and this is the matter at hand is it not? BTM do try to make money from users on here so should afford them the courtesy of support. Maybe not you but I think that is bad form. I know you have helped folk with in depth tech matters, you're an asset. BTM issues have no place on here. Why should we, as in the BT users lend time for support of a product some third party is ignorIng yet doing his best to monetize. You know me by now and what my thoughts are on things like this. I have no axe to grind with you. Again, it is my own fault spending the time without checking, I devoted a couple of hours during a busy day trying to help a few fellow BT'ers. I'm off now, just annoyed Scotland ain't in the Euros.

MacApple, Last thing I want to say about this: I totally agree what you are saying and hope that you (and anyone else) accept my apologies if I was part of wasting your valuable hours. Best Regards, Danny

Wasn't you buddy, was all me. Appreciate the sentiment though. Good man.

i take the blame, for bringing up the problem in the first place

Not a question of apportioning blame, I was the muppet here and should have checked with you before I took you down garden path so to speak. Was annoyed we missed each other on Saturday mate.

Hey Mac, sorry mate, I agree with you, just didn't express it very well! There would obviously be a very good reason why it was pulled, as such there should at the very least be a disclaimer on display for users who are unaware of the facts. Should even be in the readme text of the plugin too. fwiw, I've always found btm to be helpful and pretty quick to respond. I've got no axes to grind about anybody! One goal and you'd have been there. It's a cruel game... Lichenstein? 0-0?

When I was a kid we'd qualify all the time, sad state of affairs north of the border right now. Off to hide under a rock, said too much already tonight.

Wish I'd seen Archie Gemmill in the '78 WC as it happened! lol! Best goal ever! Just love watching goals like that.

Hi gang. I'll try to keep this as short as possible. a) We didn't "pull" the image gallery from v2.0 - it was never listed. For sure it was in v1.5 but not in v2.0. It's not a matter of security or other issues, it's simply not in the list and never was. We've done lots of experimenting while trying to find a good balance between which plugins we show in the "new and improved" v2.0 arrangement and which ones we do not. There are lots and lots of reasons we don't show dozens and dozens of plugins. Support issues are one of them. Learning curves are another one. The fact is, the more plugins there are, the more difficult it is for a new user to begin making apps that "just work." Everyone on this thread was around long before v2.0 was released but thousands of users have never used v1.5 and know nothing about "the old screens." Keep in mind that v1.5 didn't use the plugin explanation and wording. I'm just trying to say that "Screen Types" in the old way are a bit different than "plugins" and the new way. Most of us get this. b) Every plugin has a series of icons to click to learn who made it, how to contact them, how to use it, etc. If a third party plugin doesn't provide this info it's almost always assumed that we made it. This is the risk we all take when working with open source software. Pros and cons for sure. However, it's one thing to not show the creator or contact info, it's another thing again to show "buzztouch" as the creator if we are not the creator. Get it? I would be surprised if BT mods was showing our name as the creator for plugins they created from older v1.5 code. We've had this conversation before and they may have simply missed something and didn't remove our names from their download. Lots could be happening here. But...if any of you see any downloads on third party sites that are represented as "created by buzztouch" (or me, or whatever) we would appreciate the feedback. This isn't a good thing for anyone. c) The ironic part: There are only slight differences in the way the v1.5 gallery and the v2.0 setup work. This means that older v1.5 screen types could be easily used (in many cases) in the v2.0 platform. This doesn't mean you won't have to tweak some things. It just means that the older screens and the new plugins do nothing more than load a UIViewController and this UIViewController is what does all the magic for that type of feature. In this case, the gallery. The gallery in v1.5 should work in v2.0 and the JSON issue is not at all related to the fact that it's v1.5 or v2.0. Look at the way the JSON is parsed in the .m file of the plugin. It should show you what fields it's looking for and what format the JSON should be in. It's very very unlikely that anyone has re-created a different JSON format for a gallery they created. d) Third party code / support on this forum: This for sure is a good debate and worth discussing. In many cases forum users are not too stoked about helping folks with code that is non buzztouch created. Why? Because it's tough to help if you don't know what the person you're trying to help is working with. And, lots of users have invested lots of time helping buzztouch build the community, software, features, and other cool stuff we give away to many many people (99% of users pay nothing to use our backend, code, system, forum). When a third party site magically appears online with several offerings (usually for a fee) it's disingenuous to ask users "here" to help users "there." This is a simple courtesy (we think). However, it's not a bad idea totally. In some cases third parties have lots to offer. In some cases not. It's always easy to tell the difference ;-) e) Third Party Plugins: We've been working very VERY hard at trying to figure out the best way to allow folks to use third party plugins without worrying about the quality, security, consistency, and downright usefulness of their creations. It's looking like we'll end up with some sort of "vetting process" that allows us to display lots and lots of plugins for download or use in the buzztouch.com hosted service with "one click." One of the biggest challenges to this idea is that we don't want to become Apple and reject or insult or discourage folks from making new things. This means we'll end up checking third party additions for code integrity, security, and quality while trying not to worry too much about "why" this plugin was created in the first place. Example: A plugin that works well for it's purpose, that may be ridiculously simple isn't necessarily a bad thing. Just because it may not appear to be "neat" or "valuable" doesn't mean it doesn't have a purpose. Apple famously rejects very very valid ideas and we are not interested in telling folks "no, you can't list that plugin because we don't like the idea or purpose." We aim to only show / display plugins that are secure, functional, and perform as advertised - nothing more. I could go on an on about this. When the BTU learning path for Plugins is done this will make much more sense. Expect to see that learning path not only help folks get going in making neat things, but also help them get their creations in the buzztouch.com official list. This means they will get tons of exposure, lots of development opportunities, and hopefully incent them to continue making things "for us" because it's better for everyone. Time will tell.

@Raveyd Truly one of the best goals without a shadow of a doubt. To do that to Holland was just sublime. @David Cheers for chipping in, makes sense tae me!

Interesting discussion here. @ceerup Did you get your gallery working? I believe the error you are experiencing is only in the simulator. When I insert your url, it works fine in the app on my phone, but the app in the simulator crashes. I was having the same problem. Then I installed the app on my iPhone and it worked fine.

Welcome to the thread MGoBlue. Likewise when I drop the URL in 1.5 but we all know that I suppose.

Thanks, MacApple. Just my two cents here, but I think discussing third party plugins in the BT forum is good. In most cases, it will not be professional plugin developers who are building the plugins, and they may be buggy or in need of some BT super user assistance. Perhaps they should be relegated to a specific third party plugin thread. I think Danny's done a great job of modifying some of the old 1.5 code into 2.0 plugins. By sharing plugins here and allowing discussion, it helps bring about improvement to those plugins. I'd much rather have one "BT Central" forum than multiple websites and forums to find and keep track of for every new plugin that someone shares. I'm currently working on converting the 1.5 image uploader code into a plugin which I'd want to share with everyone. But the last thing I want to have to do is set up my own support forum to maintain and answer questions. If I had to do that, I'd probably not end up sharing the code -- too much work. Sorry, but that's just how it is. Now, if someone was charging for plugins, that would be a different story. You'd expect a higher level of professionalism and support. But for plugins like what Danny's built, they benefit the BT community.

Horses for courses MGoBlue. I'd love to see your work. For me it is in part about the motives behind the work. You are not trying to build a profit making business off the strength of this forum and you help out like few others can or will. 3rd party plugins that have been tested and built to work, all for them buddy, who wouldn't be. As I said above and as echoed by PSMDanny, he has done great work but he is not looking to monetize the plugins he stripped out. I reckon I've been on here close to 2 yrs and admit I can be a bit of an oppionated auld grouch at times. I'm in the minority it seems. I'm finished now, promise. No more posts or half baked rants on this thread.

My two cents: Regarding relegated to a specific third party plugin thread. A useful feature would be some required checkboxes: OS, BT version, 3rd party (I'm sure a few more would help) The category goes a long way but currently not enough categories. The basics so users are not sent down the wrong path inadvertently. "I think Danny's done a great job of modifying some of the old 1.5 code into 2.0 plugins." He's the #1 3rd party plugin developer. He may have picked some low hanging fruits (BTv1.5 code) but he picked them to Buzztouch iOS users delight. "By sharing plugins here and allowing discussion, it helps bring about improvement to those plugins." And more importantly, it builds Buzztouch knowledge base regarding plugins. "I'd much rather have one "BT Central" forum than multiple websites and forums to find and keep track of for every new plugin that someone shares." The Buzztouch Forum is certainly the appropriate place to announce plugins the van be used my Buzztouch users. Fred

Thanks everyone for the kind and nice words regarding my plugin donation. I think this discussion is good and by experiencing this, this can lead to a final solution on how (3rd party) plugins should be treated in the future. But I also think this is something you find on all open source projects. My main experience is on Joomla (an open source cms). Developers can build plugins, components and modules. For the support part on this you see it happen on multiple places: the developer site, the general joomla site (and also on the different language versions of it) and other websites related to Joomla. Joomla handles most of the extensions on a specific website (extensions.joomla.org) where users can rate, review and download the extensions. Based on the ratings and reviews you can make your choice to download/buy one of the extensions. Developers can open an account and submit details about the extension (info, version, download link, website etc). Maybe this kind of system will also work for buzztouch. I don't have the ultimate answer to a/the solution for this but maybe above will inspire to get some more ideas. Best Regards, Danny

Forum = exchange of ideas Tis all good. Despite having a view contradictory to some I agree with a lot of what has been said. If we are all in it together with a common cause and goal we'll do alright. Splinter groups divide and seldom conquer.